v1.1.0

Compare Source

Minor Changes

• Add original request object as event.platform.req (#​8171)

Patch Changes

• Updated dependencies [5426901a]:
  • @​sveltejs/kit@​1.0.5

v1.0.1

Compare Source

Patch Changes

• Update dependency @​rollup/plugin-json to v6 (#​8204)

  Note: plugin-json v6 fails your build for parse errors that only logged a warning with v5. We consider this a bugfix as only healthy input should result in a successful build.

• chore(deps): update dependency @​rollup/plugin-commonjs to v24 (#​8216)

• Updated dependencies [fab0de4f, 89b8d94b]:

  • @​sveltejs/kit@​1.0.2

v1.0.7

Compare Source

Patch Changes

• Ignore *.test.js and *.spec.js files in params directory (#​8250)

v1.0.6

Compare Source

Patch Changes

• Guarantee that $page.route has the correct shape (#​8359)

v1.0.5

Compare Source

Patch Changes

• Update typings of event.platform to be possibly undefined (#​8232)

v1.0.3

Compare Source

Patch Changes

• Include submitter's value when progressively enhancing <form method="get"> (#​8273)

v1.0.2

Compare Source

Patch Changes

• Fix filterSerializedResponseHeaders error message (#​8348)

• Fix form action redirect status code (#​8210)

v0.16.16

Compare Source

• Fix a regression caused by comment preservation (#​2805)

  The new comment preservation behavior that was added in 0.16.14 introduced a regression where comments in certain locations could cause esbuild to omit certain necessary parentheses in the output. The outermost parentheses were incorrectly removed for the following syntax forms, which then introduced syntax errors:

  (/* comment */ { x: 0 }).x;
  (/* comment */ function () { })();
  (/* comment */ class { }).prototype;

  This regression has been fixed.

v0.16.15

Compare Source

• Add format to input files in the JSON metafile data

  When --metafile is enabled, input files may now have an additional format field that indicates the export format used by this file. When present, the value will either be cjs for CommonJS-style exports or esm for ESM-style exports. This can be useful in bundle analysis.

  For example, esbuild's new Bundle Size Analyzer now uses this information to visualize whether ESM or CommonJS was used for each directory and file of source code (click on the CJS/ESM bar at the top).

  This information is helpful when trying to reduce the size of your bundle. Using the ESM variant of a dependency instead of the CommonJS variant always results in a faster and smaller bundle because it omits CommonJS wrappers, and also may result in better tree-shaking as it allows esbuild to perform tree-shaking at the statement level instead of the module level.

• Fix a bundling edge case with dynamic import (#​2793)

  This release fixes a bug where esbuild's bundler could produce incorrect output. The problematic edge case involves the entry point importing itself using a dynamic import() expression in an imported file, like this:

  // src/a.js
  export const A = 42;
  
  // src/b.js
  export const B = async () => (await import(".")).A
  
  // src/index.js
  export * from "./a"
  export * from "./b"

• Remove new type syntax from type declarations in the esbuild package (#​2798)

  Previously you needed to use TypeScript 4.3 or newer when using the esbuild package from TypeScript code due to the use of a getter in an interface in node_modules/esbuild/lib/main.d.ts. This release removes this newer syntax to allow people with versions of TypeScript as far back as TypeScript 3.5 to use this latest version of the esbuild package. Here is change that was made to esbuild's type declarations:

   export interface OutputFile {
     /** "text" as bytes */
     contents: Uint8Array;
     /** "contents" as text (changes automatically with "contents") */
  -  get text(): string;
  +  readonly text: string;
   }

v0.16.14

Compare Source

• Preserve some comments in expressions (#​2721)

  Various tools give semantic meaning to comments embedded inside of expressions. For example, Webpack and Vite have special "magic comments" that can be used to affect code splitting behavior:

  import(/* webpackChunkName: "foo" */ '../foo');
  import(/* @​vite-ignore */ dynamicVar);
  new Worker(/* webpackChunkName: "bar" */ new URL("../bar.ts", import.meta.url));
  new Worker(new URL('./path', import.meta.url), /* @​vite-ignore */ dynamicOptions);

  Since esbuild can be used as a preprocessor for these tools (e.g. to strip TypeScript types), it can be problematic if esbuild doesn't do additional work to try to retain these comments. Previously esbuild special-cased Webpack comments in these specific locations in the AST. But Vite would now like to use similar comments, and likely other tools as well.

  So with this release, esbuild now will attempt to preserve some comments inside of expressions in more situations than before. This behavior is mainly intended to preserve these special "magic comments" that are meant for other tools to consume, although esbuild will no longer only preserve Webpack-specific comments so it should now be tool-agnostic. There is no guarantee that all such comments will be preserved (especially when --minify-syntax is enabled). So this change does not mean that esbuild is now usable as a code formatter. In particular comment preservation is more likely to happen with leading comments than with trailing comments. You should put comments that you want to be preserved before the relevant expression instead of after it. Also note that this change does not retain any more statement-level comments than before (i.e. comments not embedded inside of expressions). Comment preservation is not enabled when --minify-whitespace is enabled (which is automatically enabled when you use --minify).

v1.29.2

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/19661 - [BUG] 1.29.1 browserserver + page.goto = net::ERR_SOCKS_CONNECTION_FAILED

Browser Versions

• Chromium 109.0.5414.46
• Mozilla Firefox 107.0
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 108
• Microsoft Edge 108

v1.29.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/18928 - [BUG] Electron firstWindow times out after upgrading to 1.28.0https://github.com/microsoft/playwright/issues/192466 - [BUG] Electron firstWindow times out after upgrading to 1.28.https://github.com/microsoft/playwright/issues/1941212 - [REGRESSION]: 1.28 does not work with electron-serve anymorhttps://github.com/microsoft/playwright/issues/19540540 - [BUG] electron.app.getAppPath() returns the path one level higher if you run electron pointing to the directhttps://github.com/microsoft/playwright/issues/195489548 - [REGRESSION]: Ubuntu 18 LTS not supported anymore

Browser Versions

• Chromium 109.0.5414.46
• Mozilla Firefox 107.0
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 108
• Microsoft Edge 108

v1.29.0

Compare Source

New APIs

• New method route.fetch() and new option json for route.fulfill():

  await page.route('**/api/settings', async route => {
    // Fetch original settings.
    const response = await route.fetch();
  
    // Force settings theme to a predefined value.
    const json = await response.json();
    json.theme = 'Solorized';
  
    // Fulfill with modified data.
    await route.fulfill({ json });
  });

• New method locator.all() to iterate over all matching elements:

  // Check all checkboxes!
  const checkboxes = page.getByRole('checkbox');
  for (const checkbox of await checkboxes.all())
    await checkbox.check();

• Locator.selectOption matches now by value or label:

  <select multiple>
    <option value="red">Red</div>
    <option value="green">Green</div>
    <option value="blue">Blue</div>
  </select>

  await element.selectOption('Red');

• Retry blocks of code until all assertions pass:

  await expect(async () => {
    const response = await page.request.get('https://api.example.com');
    await expect(response).toBeOK();
  }).toPass();

  Read more in our documentation.

• Automatically capture full page screenshot on test failure:

  // playwright.config.ts
  import type { PlaywrightTestConfig } from '@​playwright/test';
  
  const config: PlaywrightTestConfig = {
    use: {
      screenshot: {
        mode: 'only-on-failure',
        fullPage: true,
      }
    }
  };
  
  export default config;

Miscellaneous

• Playwright Test now respects jsconfig.json.
• New options args and proxy for androidDevice.launchBrowser().
• Option postData in method route.continue() now supports serializable values.

Browser Versions

• Chromium 109.0.5414.46
• Mozilla Firefox 107.0
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 108
• Microsoft Edge 108

v7.23.0

Compare Source

Minor Changes

• When the resolve-peers-from-workspace-root setting is set to true, pnpm will use dependencies installed in the root of the workspace to resolve peer dependencies in any of the workspace's projects #​5882.

Patch Changes

• The help of the run command should list the --resume-from option.
• Should display --include-workspace-root option on recursive command's help info.

Our Gold Sponsors

Our Silver Sponsors

v8.4.21

Compare Source

• Fixed Input#error types (by Aleks Hudochenkov).

v2.8.2

Compare Source

diff

Don't lowercase link references (#​13155 by @​DerekNonGeneric & @​fisker)

<!-- Input -->
We now don't strictly follow the release notes format suggested by [Keep a Changelog].

[Keep a Changelog]: https://example.com/

<!-- Prettier 2.8.1 -->
We now don't strictly follow the release notes format suggested by [Keep a Changelog].

[keep a changelog]: https://example.com/
<!--
^^^^^^^^^^^^^^^^^^ lowercased
-->

<!-- Prettier 2.8.2 -->
<Same as input>

Preserve self-closing tags (#​13691 by @​dcyriller)

{{! Input }}
<div />
<div></div>
<custom-component />
<custom-component></custom-component>
<i />
<i></i>
<Component />
<Component></Component>

{{! Prettier 2.8.1 }}
<div></div>
<div></div>
<custom-component></custom-component>
<custom-component></custom-component>
<i></i>
<i></i>
<Component />
<Component />

{{! Prettier 2.8.2 }}
<div />
<div></div>
<custom-component />
<custom-component></custom-component>
<i />
<i></i>
<Component />
<Component />

Allow custom "else if"-like blocks with block params (#​13930 by @​jamescdavis)

#​13507 added support for custom block keywords used with else, but failed to allow block params. This updates printer-glimmer to allow block params with custom "else if"-like blocks.

{{! Input }}
{{#when isAtWork as |work|}}
  Ship that
  {{work}}!
{{else when isReading as |book|}}
  You can finish
  {{book}}
  eventually...
{{else}}
  Go to bed!
{{/when}}

{{! Prettier 2.8.1 }}
{{#when isAtWork as |work|}}
  Ship that
  {{work}}!
{{else when isReading}}
  You can finish
  {{book}}
  eventually...
{{else}}
  Go to bed!
{{/when}}

{{! Prettier 2.8.2 }}
{{#when isAtWork as |work|}}
  Ship that
  {{work}}!
{{else when isReading as |book|}}
  You can finish
  {{book}}
  eventually...
{{else}}
  Go to bed!
{{/when}}

Preserve empty lines between nested SCSS maps (#​13931 by @​jneander)

/* Input */
$map: (
  'one': (
     'key': 'value',
  ),

  'two': (
     'key': 'value',
  ),
)

/* Prettier 2.8.1 */
$map: (
  'one': (
     'key': 'value',
  ),
  'two': (
     'key': 'value',
  ),
)

/* Prettier 2.8.2 */
$map: (
  'one': (
     'key': 'value',
  ),

  'two': (
     'key': 'value',
  ),
)

Fix missing parentheses when an expression statement starts with let[ (#​14000, #​14044 by @​fisker, @​thorn0)

// Input
(let[0] = 2);

// Prettier 2.8.1
let[0] = 2;

// Prettier 2.8.1 (second format)
SyntaxError: Unexpected token (1:5)
> 1 | let[0] = 2;
    |     ^
  2 |

// Prettier 2.8.2
(let)[0] = 2;

Fix semicolon duplicated at the end of LESS file (#​14007 by @​mvorisek)

// Input
@​variable: {
  field: something;
};

// Prettier 2.8.1
@​variable: {
  field: something;
}; ;

// Prettier 2.8.2
@​variable: {
  field: something;
};

Fix no space after unary minus when followed by opening parenthesis in LESS (#​14008 by @​mvorisek)

// Input
.unary_minus_single {
  margin: -(@​a);
}

.unary_minus_multi {
  margin: 0 -(@​a);
}

.binary_minus {
  margin: 0 - (@​a);
}

// Prettier 2.8.1
.unary_minus_single {
  margin: - (@​a);
}

.unary_minus_multi {
  margin: 0 - (@​a);
}

.binary_minus {
  margin: 0 - (@​a);
}

// Prettier 2.8.2
.unary_minus_single {
  margin: -(@​a);
}

.unary_minus_multi {
  margin: 0 -(@​a);
}

.binary_minus {
  margin: 0 - (@​a);
}

Do not change case of property name if inside a variable declaration in LESS (#​14034 by @​mvorisek)

// Input
@​var: {
  preserveCase: 0;
};

// Prettier 2.8.1
@​var: {
  preservecase: 0;
};

// Prettier 2.8.2
@​var: {
  preserveCase: 0;
};

Fix formatting for auto-accessors with comments (#​14038 by @​fisker)

// Input
class A {
  @​dec()
  // comment
  accessor b;
}

// Prettier 2.8.1
class A {
  @​dec()
  accessor // comment
  b;
}

// Prettier 2.8.1 (second format)
class A {
  @​dec()
  accessor; // comment
  b;
}

// Prettier 2.8.2
class A {
  @​dec()
  // comment
  accessor b;
}

Add parentheses for TSTypeQuery to improve readability (#​14042 by @​onishi-kohei)

// Input
a as (typeof node.children)[number]
a as (typeof node.children)[]
a as ((typeof node.children)[number])[]

// Prettier 2.8.1
a as typeof node.children[number];
a as typeof node.children[];
a as typeof node.children[number][];

// Prettier 2.8.2
a as (typeof node.children)[number];
a as (typeof node.children)[];
a as (typeof node.children)[number][];

Fix displacing of comments in default switch case (#​14047 by @​thorn0)

It was a regression in Prettier 2.6.0.

// Input
switch (state) {
  default:
    result = state; // no change
    break;
}

// Prettier 2.8.1
switch (state) {
  default: // no change
    result = state;
    break;
}

// Prettier 2.8.2
switch (state) {
  default:
    result = state; // no change
    break;
}

Support type annotations on auto accessors via babel-ts (#​14049 by @​sosukesuzuki)

The bug that @babel/parser cannot parse auto accessors with type annotations has been fixed. So we now support it via babel-ts parser.

class Foo {
  accessor prop: number;
}

Fix formatting of empty type parameters (#​14073 by @​fisker)

// Input
const foo: bar</* comment */> = () => baz;

// Prettier 2.8.1
Error: Comment "comment" was not printed. Please report this error!

// Prettier 2.8.2
const foo: bar</* comment */> = () => baz;

Add parentheses to head of ExpressionStatement instead of the whole statement (#​14077 by @​fisker)

// Input
({}).toString.call(foo) === "[object Array]"
  ? foo.forEach(iterateArray)
  : iterateObject(foo);

// Prettier 2.8.1
({}.toString.call(foo) === "[object Array]"
  ? foo.forEach(iterateArray)
  : iterateObject(foo));

// Prettier 2.8.2
({}).toString.call(foo.forEach) === "[object Array]"
  ? foo.forEach(iterateArray)
  : iterateObject(foo);

Fix comments after directive (#​14081 by @​fisker)

// Input
"use strict" /* comment */;

// Prettier 2.8.1 (with other js parsers except `babel`)
Error: Comment "comment" was not printed. Please report this error!

// Prettier 2.8.2
<Same as input>

Fix formatting for comments inside JSX attribute (#​14082 with by @​fisker)

// Input
function MyFunctionComponent() {
  <button label=/*old*/"new">button</button>
}

// Prettier 2.8.1
Error: Comment "old" was not printed. Please report this error!

// Prettier 2.8.2
function MyFunctionComponent() {
  <button label=/*old*/ "new">button</button>;
}

Quote numeric keys for json-stringify parser (#​14083 by @​fisker)

// Input
{0: 'value'}

// Prettier 2.8.1
{
  0: "value"
}

// Prettier 2.8.2
{
  "0": "value"
}

Fix removing commas from function arguments in maps (#​14089 by @​sosukesuzuki)

/* Input */
$foo: map-fn(
  (
    "#{prop}": inner-fn($first, $second),
  )
);

/* Prettier 2.8.1 */
$foo: map-fn(("#{prop}": inner-fn($first $second)));

/* Prettier 2.8.2 */
$foo: map-fn(
  (
    "#{prop}": inner-fn($first, $second),
  )
);

Do not insert space in LESS property access (#​14103 by @​fisker)

// Input
a {
  color: @​colors[@​white];
}

// Prettier 2.8.1
a {
  color: @​colors[ @​white];
}

// Prettier 2.8.2
<Same as input>

v0.27.0

Compare Source

   🚨 Breaking Changes

• Deprecate "error" on result, store errors in "errors"  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2586 (e641a)
• Split vitest into separate packages, but still bundle them for the time being  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2575 (c8e6f)

   🚀 Features

• coverage: report only changed files when using istanbul coverage with watch mode  -  by @​g4rry420 in https://github.com/vitest-dev/vitest/issues/2385 (bf872)

   🐞 Bug Fixes

• Return mock path only when mocked  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2619 (f8ac2)
• Allow mocking CJS module with interoped default  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2598 (6b3e3)
• Avoid random ENOTEMPTY errors  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/2620 (59766)
• Always inline assets and modules with special Vite queries  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2617 (fed1c)
• cli:
  • Allow overrides reporter via cli option  -  by @​mysteryven and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2573 (894f1)
• coverage:
  • Flaky c8 coverage caused by parallel sourcemap constructing  -  by @​AriPerkkio and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2591 (9a29f)
  • Validate extension, when reporting c8 coverage  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2626 (74463)

   🏎 Performance

• Improve vi.mock performance  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2594 (09d19)

    View changes on GitHub